[PM-40510] feat: rename vault-filter query param to sharedFolderId#21968
[PM-40510] feat: rename vault-filter query param to sharedFolderId#21968jaasen-livefront wants to merge 2 commits into
Conversation
…erId Behind the vfo1-foundation flag, RoutedVaultFilterService now reads both sharedFolderId and legacy collectionId query params (preferring the new one) and, in createRoute(), writes sharedFolderId while nulling collectionId when the flag is on (reverse when off). Split from PM-40252 (terminology-only).
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE Reviewed the rename of the vault-filter query param from Code Review DetailsNo findings. The change is small, symmetric, behind an off-by-default flag, and well tested for the new logic. The type assertions ( |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #21968 +/- ##
==========================================
- Coverage 52.44% 52.44% -0.01%
==========================================
Files 4130 4130
Lines 130572 130574 +2
Branches 20494 20495 +1
==========================================
Hits 68475 68475
+ Misses 57045 57036 -9
- Partials 5052 5063 +11 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-40510
📔 Objective
Behind the
vfo1-foundationfeature flag (off by default), rename the vault-filter query param fromcollectionIdtosharedFolderIdin the sharedRoutedVaultFilterService:filter$) accepts bothsharedFolderIdand legacycollectionId(preferring the new one), so existing/bookmarked?collectionId=links keep working during the transition. TheRoutedVaultFilterModel.collectionIdfield name is unchanged — only the URL param is renamed.createRoute()writessharedFolderIdand nullscollectionIdwhen the flag is on; writescollectionIdand nullssharedFolderIdwhen off (queryParamsHandling: "merge"clears the stale param).Split from PM-40252 (terminology-only) — it is the only routing/behavioral change and is coupled to the per-client reader/writer migrations. App-level direct query-param readers/writers (apps/web
vault.component,vault-collection-actions.service; apps/browsernew-item-page) are migrated in the per-client tickets; until then the flag stays off, so no broken window.